Cloud-based trash-can

ABSTRACT

Technologies are generally described for a cloud-based trash-can. In some examples, a method performed under control of a user device may include displaying a remote trash-can icon on a display of the user device, receiving a first user input that includes moving an icon representing a locally stored file to be discarded onto the remote trash-can icon, displaying on the display a request for a reason for discarding the locally stored file, and moving the discarded file to a server.

BACKGROUND

An icon for a trash-can or recycle bin on a computer desktop representsa folder that temporarily stores any files that are intended fordeletion. Since a user who has deleted a file can change his/her mindand decide to recover the deleted file, many operating systems provide atrash-can function. In particular, some operating systems supportinggraphical user interfaces (GUI), such as Apple Mac OS or MicrosoftWindows, provide a trash-can icon, so that the user can easily delete afile by dragging and dropping the file to the trash-can icon.

SUMMARY

In an example, a method performed under control of a user device mayinclude displaying a remote trash-can icon on a display of the userdevice, receiving a first user input that includes moving an iconrepresenting a locally stored file to be discarded onto the remotetrash-can icon, displaying on the display a request for a reason fordiscarding the locally stored file, and moving the discarded file to aserver.

In an example, a method performed under control of a user device mayinclude displaying a plurality of remote trash-can icons on a display ofthe user device, receiving a user input that includes moving an iconrepresenting a locally stored file to be discarded onto one of theplurality of remote trash-can icons, and moving the discarded file to aserver.

In an example, a method performed under control of a server may includereceiving from a user device a file discarded on the user device,receiving from the user device a reason for discarding the file, andstoring the file and the reason locally.

In an example, a user device may include a display configured to displaya remote trash-can icon, a storage configured to store at least onefile, a user input handling unit configured to receive a first userinput that includes moving an icon representing at least one of thestored files to be discarded onto the remote trash-can icon, a controlunit configured to generate a request for a reason for discarding the atleast one file, the request being configured to be displayed on thedisplay, and a transmitting unit configured to move the at least onediscarded file to a server.

In an example, a user device may include a display configured to displaya plurality of remote trash-can icons, a storage configured to store atleast one file, a user input handling unit configured to receive a userinput that includes moving an icon representing at least one of thestored files to be discarded onto one of the plurality of remotetrash-can icons, and a transmitting unit configured to move the at leastone discarded file to a server.

In an example, a server may include a receiving unit configured toreceive from a user device a discarded file and a reason for discardingthe discarded file, and a storage configured to store the discarded fileand the reason.

In an example, a computer-readable storage medium may store thereoncomputer-executable instructions that, in response to execution, cause auser device to perform operations, including displaying a remotetrash-can icon on a display of the user device, receiving a first userinput that includes moving an icon representing a locally stored file tobe discarded onto the remote trash-can icon, displaying on the display arequest for a reason for discarding the locally stored file, and movingthe discarded file to a server.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other features of this disclosure will become moreapparent from the following description and appended claims, taken inconjunction with the accompanying drawings. Understanding that thesedrawings depict only several embodiments in accordance with thedisclosure and are, therefore, not to be considered limiting of itsscope, the disclosure will be described with additional specificity anddetail through use of the accompanying drawings, in which:

FIG. 1 schematically shows a cloud-based trash-can system, arranged inaccordance with at least some embodiments described herein;

FIGS. 2(A) and 2(B) schematically show illustrative examples ofscreenshots of a user device displaying a remote trash-can icon,arranged in accordance with at least some embodiments described herein;

FIG. 3 schematically shows an illustrative example of a screenshot of auser device displaying multiple remote trash-can icons, arranged inaccordance with at least some embodiments described herein;

FIG. 4 shows a schematic block diagram illustrating an examplearchitecture of a user device, arranged in accordance with at least someembodiments described herein;

FIG. 5 shows a schematic block diagram illustrating an examplearchitecture of a server, arranged in accordance with at least someembodiments described herein;

FIG. 6 shows an example flow diagram of a process performed undercontrol of a user device for providing a remote trash-can function,arranged in accordance with at least some embodiments described herein;

FIG. 7 shows another example flow diagram of a process performed undercontrol of a user device for providing a remote trash-can function,arranged in accordance with at least some embodiments described herein;

FIG. 8 shows an example flow diagram of a process performed undercontrol of a server for providing a remote trash-can function, arrangedin accordance with at least some embodiments described herein;

FIG. 9 illustrates example computer program products that may beutilized to provide a remote trash-can function, arranged in accordancewith at least some embodiments described herein; and

FIG. 10 is a block diagram illustrating an example computing device thatmay be utilized to provide a remote trash-can function, arranged inaccordance with at least some embodiments described herein.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented herein. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe drawings, can be arranged, substituted, combined, separated, anddesigned in a wide variety of different configurations, all of which areexplicitly contemplated herein.

This disclosure is generally drawn, inter alia, to methods, apparatuses,systems, devices, and computer program products related to a cloud-basedtrash-can.

Technologies are generally described for a remote trash-can serviceprovided by a server. In some examples, a user device, subscribing tothe remote trash-can service provided by the server, may display aremote trash-can icon on a display thereof, so that a user of the userdevice may discard or delete a file from the user device and temporarilystore the discarded file on the server, by dragging and dropping a fileicon representing the file to be discarded onto the remote trash-canicon.

In some examples, when the user moves the file icon onto the remotetrash-can icon, a user interface on the user device may display arequest for a reason for discarding the file, for example, in a form ofa dialog box. By way of example, but not limitation, the request mayinclude an interactive menu that includes representations of variousreasons for file deletion, such as, for example, “not interesting,”“lack of local storage,” “content duplication,” and so on. In someexamples, the menu of reasons may vary depending on a type of the fileto be discarded. That is, the dialog box may provide a menu of reasonsfor discarding a document file that are different for those fordiscarding a picture file or a video file. These examples are notintended to be limiting.

In some examples, when the user responds to the request, the user devicemay send to the server the response of the user along with the file. Insome examples, the user device may also send to the server fileinformation including the file's name, contents, date of creation,location of creation, and/or date of last update, etc. In some examples,the user device may also send to the server information regarding thefile deletion, including a time and/or a location of the user's actionof discarding the file.

In some examples, the user device may display multiple remote trash-canicons on the display. The multiple remote trash-can icons may berespectively associated with different reasons for file deletion suchas, for example, “not interesting,” “lack of local storage,” “contentduplication,” and so on, so that the user may selectively discard thefile by dragging and dropping the file icon onto one of the remotetrash-can icons. In some examples, when the user moves the file icononto the one of the remote trash-can icons, the user device may send tothe server the reason for file deletion associated with thecorresponding remote trash-can icon, along with the file.

In some examples, when the server receives from the user device the filediscarded on the user device and the reason for file deletion, theserver may store the file and the reason thereon. In some examples, theserver may also store the file information, including but not limited tothe name, the contents, the date of creation, the location of creation,and/or the date of last update, which may be received from the userdevice. In some examples, the server may also store the informationregarding the file deletion, including the time and/or the location ofthe user's action of discarding the file, which may be received from theuser device.

In some examples, the server may examine the user's action of filedeletion based on the reason for file deletion, and provide results ofexamination to other service providers and/or content providers. By wayof example, but not limitation, when the user discards an applicationprogram, the server may provide the results of examination including thereason for file deletion to a developer of the discarded applicationprogram or other application developers interested in the examination.By way of example, but not limitation, when the user discards an imagefile, the server may provide the results of examination including thereason for file deletion and/or the file information to a photoretouching software developer and/or a digital camera manufacturer. Byway of another example, but not limitation, when the user discards anaudio file, the server may provide the results of examination includingthe reason for file deletion and/or the file information to a musiccontent provider for trend detection and/or prediction. By way of yetanother example, but not limitation, when certain files show a tendencyof being discarded simultaneously, the server may provide the results ofexamination to a relevant software developer to develop a newapplication for handling these discarded files together. By way ofexample, but not limitation, when the user tends to simultaneouslydiscard multiple photo files captured on a same day, the server mayprovide the results of examination to a photo management softwaredeveloper, so as to develop an application managing photo files based onthe capture dates of the respective photo files. By way of anotherexample, but not limitation, when the user tends to simultaneouslydiscard a video file, a music file, and an image file with a videomaking project file, the server may provide the results of examinationto a video editing software, so as to develop an application having afunction of deleting all the files related to the video making projectfile when the user deletes the video making project file.

FIG. 1 schematically shows a cloud-based trash-can system, arranged inaccordance with at least some embodiments described herein.

As depicted, a cloud-based trash-can system 100 may include a server 110and a user device 120. Server 110 and user device 120 may communicatewith each other via a network 130. By way of example, but notlimitation, the server may be managed or operated by a data centeroperator or a cloud-based storage provider. Examples of user device 120may include, but are not limited to, a tablet, a smartphone, a mobilephone, a personal digital assistant (PDA), a mobile game console, alaptop computer, a desktop computer, or any other devices being able toaccess server 110. Examples of network 130 may include, but are notlimited to, a local area network (LAN), a backbone network, ametropolitan area network (MAN), a wide area network (WAN), a virtualprivate network (VPN), an internetwork, etc.

In some embodiments, when user device 120 subscribes to a cloud-basedtrash-can service provided on server 110, user device 120 may display aremote trash-can icon 210, in addition to or instead of a localtrash-can icon 220, as depicted in FIG. 2(A). In such cases, when a userof user device 120 wants to discard a file from user device 120 andtemporarily store the discarded file on server 110, the user may dragand drop, i.e., move, a file icon representing the file to be discardedonto remote trash-can icon 210, by using, for example, an external inputdevice such as a mouse, a touch pad, a touch screen, a trackball and/ora drawing tablet, and/or via a voice command, depending on desiredimplementations. Meanwhile, when the user wants to discard the file butstill temporarily store the discarded file on user device 120, the usermay drag and drop the file icon onto local trash-can icon 220. In someembodiments, remote trash-can icon 210 may have a different color, shapeand/or name from those of local trash-can icon 220, so that the twoicons may be distinguished from each other.

In some embodiments, when the user moves the file icon onto remotetrash-can icon 210, a user interface on user device 120 may display arequest for a reason for discarding the file, for example, in a form ofa dialog box 230, as depicted in FIG. 2(B). Dialog box 230 may include aquestion 240 regarding a reason for discarding the file, and candidateanswers 250-1, 250-2, 250-3 and 250-4, which may be representations ofvarious reasons for discarding the file. By way of example, but notlimitation, dialog box 230 may include question 240 of “why do you wantto discard the file?” and candidate answers of “not interesting”(250-1), “lack of local storage” (250-2), “content duplication” (250-3),and “other reasons” (250-4).

In some embodiments, candidate answers 250-1, 250-2, 250-3 and 250-4 mayvary depending on a type of the file to be discarded. By way of example,but not limitation, when the file to be discarded is a preinstalledapplication, candidate answers 250-1, 250-2, 250-3 and 250-4 may includeat least one of “not interesting,” “lack of local storage,” “tried usingbut found useless,” “found a bug,” and so on. By way of example, but notlimitation, when the file to be discarded is a photo, candidate answers250-1, 250-2, 250-3 and 250-4 may include at least one of “camera notsteady,” “out of focus,” “inadequate exposure,” “unsatisfactorycomposition,” and so on. Although FIG. 2(B) illustrates that dialog box230 shows four candidate answers 250-1, 250-2, 250-3 and 250-4, itshould be appreciated by one skilled in the relevant art that dialog box230 may show any number of candidate answers depending on desiredimplementations.

In some embodiments, when the user makes a response to the request byselecting one of candidate answers 250-1, 250-2, 250-3 and 250-4, userdevice 120 may send to server 110 the response, i.e., the reason fordiscarding the file. In some embodiments, the user may be rewarded bythe data center operator or the cloud-based storage provider, whenmaking the response to the request. By way of example, but notlimitation, when the user responds to the request, the user may get morestorage space, get points for services provided by server 110 or otherservices, and so on.

In some embodiments, user device 120 may not always display dialog box230 whenever the user moves the file icon onto remote trash-can icon210. That is, user device 120 may adjust frequency of displaying ofdialog box 230. In some embodiments, when the user prefers not to reportreasons for discarding files to server 110, the user interface on userdevice 120 may forego displaying dialog box 230.

In some embodiments, user device 120 may also send to server 110information about the discarded file. By way of example, but notlimitation, the transmitted information about the discarded file mayinclude at least one of a name, contents, a date of creation, a locationof creation, and a date of last update.

In some embodiments, user device 120 may also send to server 110information about the user's input or action of discarding the file. Byway of example, but not limitation, the transmitted information aboutthe user's input or action of discarding the file may include at leastone of a time and a location of the user's input or action.

In some embodiments, user device 120 may also send to server 110information about user device 120 such as, for example, a unique deviceidentifier of user device 120. The information about user device 120 mayinclude information regarding the user such as, for example, age, sex,place of residence, purchasing site, etc. of the user, that may be usedfor the aforementioned examination.

In some embodiments, as depicted in FIG. 3, user device 120 may displaymultiple remote trash-can icons 310-1, 310-2, 310-3 and 310-4. AlthoughFIG. 3 illustrates that user device 120 displays four remote trash-canicons 310-1, 310-2, 310-3 and 310-4, it should be appreciated by oneskilled in the relevant art that user device 120 may display any numberof remote trash-can icons depending on desired implementations.

In some embodiments, multiple remote trash-can icons 310-1, 310-2, 310-3and 310-4 may be respectively associated with different reasons fordiscarding the file. By way of example, but not limitation, remotetrash-can icon 310-1 may be associated with “not interesting,” remotetrash-can icon 320-2 may be associated with “lack of local storage,”remote trash-can icon 320-3 may be associated with “contentduplication,” and remote trash-can icon 320-4 may be associated with“other reasons.” The reasons for discarding the file may vary dependingon a type of the file to be discarded, as described above with referenceto FIG. 2(B). Alternatively, each of trash-can icons 310-1, 310-2,310-3, and 310-4 may correspond to different types of discarded files,e.g., applications, documents, photos, videos.

In some embodiments, user device 120 may display multiple remotetrash-can icons 310-1, 310-2, 310-3 and 310-4 with different colors,shapes and/or names, so that multiple remote trash-can icons 310-1,310-2, 310-3 and 310-4 may be distinguished from one another.

In some embodiments, when the user wants to discard the file from userdevice 120 and temporarily store the discarded file in server 110, theuser may select one of multiple remote trash-can icons 310-1, 310-2,310-3 and 310-4 based on the reason for discarding the file, and dragand drop the file icon representing the file to be discarded onto theselected one of multiple remote trash-can icons 310-1, 310-2, 310-3 and310-4. In such cases, user device 120 may send to server 110 the reasonfor discarding the file associated the selected one of multiple remotetrash-can icons 310-1, 310-2, 310-3 and 310-4.

In some embodiments, user device 120 may also send to server 110 theinformation about the discarded file, the information about the user'sinput or action of discarding the file, and/or the information aboutuser device 120, as described above with reference to FIGS. 2(A)-(B).

In some embodiments, server 110 may receive and store thereon the filediscarded from user device 120 and the reason for discarding the file.In some embodiments, server 110 may also receive and store thereon theinformation about the discarded file, the information about the user'sinput or action of discarding the file, and/or the information aboutuser device 120.

In some embodiments, server 110 may examine the reason for discardingthe file, and at least one of the information about the file, theinformation about the user's input or action of discarding the file, andthe information about user device 120, so that server 110, other serviceproviders and/or content providers may utilize results of theexamination.

Although the above examples with regard to FIGS. 1-3 illustrate that theuser discards a file from user device 120 and temporarily stores thediscarded file on server 110 by moving a file icon representing the fileto be discarded onto remote trash-can icon 210 or remote trash-can icons310-1, 310-2, 310-3 and 310-4, those skilled in the art will recognizethat the user may also discard any data, which is not represented as afile, in a same or similar way. Those skilled in the art will alsorecognize that the user may also discard a file in server 110 andtemporarily store the discarded file on server 110 in a same or similarway.

FIG. 4 shows a schematic block diagram illustrating an examplearchitecture of a user device, arranged in accordance with at least someembodiments described herein.

As depicted, user device 120 may include a display 410, a storage 420, auser input handling unit 430, a control unit 440, and a transmittingunit 450. Although illustrated as discrete components, variouscomponents may be divided into additional components, combined intofewer components, or eliminated while being contemplated within thescope of the disclosed subject matter.

Display 410 may be configured to display a remote trash-can icon (e.g.,remote trash-can icon 210) or multiple remote trash-can icons (e.g.,remote trash-can icons 310-1, 310-2, 310-3 and 310-4) on a userinterface, depending on desired implementations. In some embodiments,the multiple remote trash-can icons may be respectively associated withdifferent reasons for file deletion.

Storage 420 may be configured to store at least one file.

User input handling unit 430 may be configured to receive a first userinput intended to discard a file from storage 420 and temporarily storethe file in a cloud-based server such as server 110. In someembodiments, the first user input may include moving a file iconrepresenting the file to be discarded onto remote trash-can icon 210 orone of multiple remote trash-can icons 310-1, 310-2, 310-3 and 310-4displayed on display 410.

Control unit 440 may be configured to generate a request for a reasonfor discarding the file (e.g., dialog box 230), when user input handlingunit 430 receives the first user input of moving the file icon ontoremote trash-can icon 210. The request generated by control unit 440 maybe displayed on display 410, and a response to the request may bereceived by user input handling unit 430 as a second user input.

Transmitting unit 450 may be configured to transmit or move the file toserver 110. In some embodiments, transmitting unit 450 may be furtherconfigured to transmit to server 110 the reason for discarding the file(i.e., the second user input or one of the reasons for file deletionassociated with the one of the multiple remote trash-can icons). In someembodiments, transmitting unit 450 may further transmit to server 110 atleast one of information about the discarded file, information about thefirst and/or second user inputs, and information about user device 120.

FIG. 5 shows a schematic block diagram illustrating an examplearchitecture of a server, arranged in accordance with at least someembodiments described herein.

As depicted, server 110 may include a receiving unit 510, a storage 520,and an information examination unit 530. Although illustrated asdiscrete components, various components may be divided into additionalcomponents, combined into fewer components, or eliminated while beingcontemplated within the scope of the disclosed subject matter.

Receiving unit 510 may be configured to receive, from a user device suchas user device 120, a file discarded from user device 120 and a reasonfor discarding the file. In some embodiments, receiving unit 510 mayalso receive from user device 120 at least one of information about thediscarded file, information about the discarding of the discarded file,and information about user device 120.

Storage 520 may be configured to store the discarded file and theaccompanying reason for being discarded. In some embodiments, when userdevice 120 requests restoration of the file, the discarded file storedin storage 520 may be transmitted to user device 120.

Information examination unit 530 may be configured to examine the reasonfor discarding the discarded file and the information received from userdevice 120. In some embodiments, examination results from informationexamination unit 530 may be provided to other service providers and/orcontent providers.

FIG. 6 shows an example flow diagram of a process performed undercontrol of a user device for providing a remote trash-can function,arranged in accordance with at least some embodiments described herein.

The process in FIG. 6 may be implemented in a user device, such as userdevice 120 including display 410, storage 420, user input handling unit430, control unit 440 and transmitting unit 450 described above. Anexample process 600 may include one or more operations, actions, orfunctions as illustrated by one or more blocks 610, 620, 630, 640 and/or650. Although illustrated as discrete blocks, various blocks may bedivided into additional blocks, combined into fewer blocks, oreliminated, depending on the desired implementation. Processing maybegin at block 610.

At block 610 (Display Remote Trash-Can Icon), the user device maydisplay a remote trash-can icon (e.g., remote trash-can icon 210) on adisplay of the user device. The user device may display the remotetrash-can icon in addition to a local trash-can icon or instead of thelocal trash-can icon. Processing may continue from block 610 to block620.

At block 620 (Receive First User Input), the user device may receive afirst user input intended to discard a locally stored file from the userdevice and temporarily store the file in a server (e.g., server 110). Insome embodiments, the first user input may include moving an iconrepresenting the file to be discarded onto the remote trash-can icon.Processing may continue from block 620 to block 630.

At block 630 (Display Request for Reason for Discarding File), the userdevice may display on the display a request for a reason for discardingthe file. In some embodiments, the request may include an interactivemenu including representations of various reasons for discarding thefile. In some embodiments, the request may vary based at least in parton a type of the discarded file. Processing may continue from block 630to block 640.

At block 640 (Receive Second User Input), the user device may receive asecond user input that is a response to the request. Processing maycontinue from block 640 to block 650.

At block 650 (Transmit Discarded File and Second User Input to Server),the user device may transmit to the server the discarded file and thesecond user input. In some embodiments, the user device may alsotransmit to the server at least one of information about the discardedfile (e.g., a name, contents, a date of creation, a location ofcreation, and/or a date of last update of the discarded file),information about the first user input (e.g., a time and/or a locationof the first user input), and information about the user device (e.g., adevice identifier of the user device).

FIG. 7 shows another example flow diagram of a process performed undercontrol of a user device for providing a remote trash-can function,arranged in accordance with at least some embodiments described herein.

The process in FIG. 7 may be implemented in a user device, such as userdevice 120 including display 410, storage 420, user input handling unit430 and transmitting unit 450 described above. An example process 700may include one or more operations, actions, or functions as illustratedby one or more blocks 710, 720 and/or 730. Although illustrated asdiscrete blocks, various blocks may be divided into additional blocks,combined into fewer blocks, or eliminated, depending on the desiredimplementation. Processing may begin at block 710.

At block 710 (Display Multiple Remote Trash-Can Icons), the user devicemay display multiple remote trash-can icons (e.g., remote trash-canicons 310-1, 310-2, 310-3 and 310-4) on a display of the user device. Insome embodiments, multiple remote trash-can icons may respectivelyrelate to different reasons for discarding locally stored files.Processing may continue from block 710 to block 720.

At block 720 (Receive User Input), the user device may receive a userinput intended to discard one of the locally stored files from the userdevice and temporarily store the file in a server (e.g., server 110). Insome embodiments, the user input may include moving an icon representingthe file to be discarded onto one of the multiple remote trash-canicons. Processing may continue from block 720 to block 730.

At block 730 (Transmit Discarded File and Reason for Discarding toServer), the user device may transmit to the server the discarded fileand a reason for discarding the file that is related to the remotetrash-can icon onto which the icon has been moved. In some embodiments,the user device may also transmit to the server at least one ofinformation about the discarded file (e.g., a name, contents, a date ofcreation, a location of creation, and/or a date of last update of thediscarded file), information about the user input (e.g., a time and/or alocation of the user input), and information about the user device(e.g., a device identifier of the user device).

FIG. 8 shows an example flow diagram of a process performed undercontrol of a server for providing a remote trash-can function, arrangedin accordance with at least some embodiments described herein.

The process in FIG. 8 may be implemented in a server, such as server 110including receiving unit 510, storage 520 and information examinationunit 530 described above. An example process 800 may include one or moreoperations, actions, or functions as illustrated by one or more blocks810 and/or 820. Although illustrated as discrete blocks, various blocksmay be divided into additional blocks, combined into fewer blocks, oreliminated, depending on the desired implementation. Processing maybegin at block 810.

At block 810 (Receive File Discarded on User Device and Reason forDiscarding), the server may receive from a user device (e.g., userdevice 120) a file discarded on the user device and a reason fordiscarding the file. In some embodiments, the server may also receivefrom the user device at least one of information about the file (e.g., aname, contents, a date of creation, a location of creation, and/or adate of last update of the file), information about the discarding ofthe file (e.g., a time and/or a location of the discarding of the fileby a user of the user device), and information about the user device(e.g., a device identifier of the user device), which may be used foradditional analysis. Processing may continue from block 810 to block820.

At block 820 (Store File and Reason), the server may store the receivedfile together with the reason for discarding the file.

One skilled in the art will appreciate that, for these and otherprocesses and methods disclosed herein, the functions performed in theprocesses and methods may be implemented in differing order.Furthermore, the outlined steps and operations are only provided asexamples, and some of the steps and operations may be optional, combinedinto fewer steps and operations, or expanded into additional steps andoperations without detracting from the essence of the disclosedembodiments.

FIG. 9 illustrates example computer program products that may beutilized to provide a remote trash-can function, arranged in accordancewith at least some embodiments described herein.

Program product 900 may include a signal bearing medium 902. Signalbearing medium 902 may include one or more instructions 904 that, whenexecuted by, for example, a processor of a user device, may provide thefunctionality described above with respect to FIGS. 1-8. By way ofexample, instructions 904 may include: one or more instructions fordisplaying a remote trash-can icon on a display of the user device; oneor more instructions for receiving a first user input that includesmoving an icon representing a locally stored file to be discarded ontothe remote trash-can icon; one or more instructions for displaying onthe display a request for a reason for discarding the locally storedfile; one or more instructions for moving the discarded file to aserver. Thus, for example, referring to FIG. 4, user device 120 mayundertake one or more of the blocks shown in FIGS. 6-7 in response toinstructions 904.

In some implementations, signal bearing medium 902 may encompass acomputer-readable medium 906, such as, but not limited to, a hard diskdrive, a CD, a DVD, a digital tape, memory, etc. In someimplementations, signal bearing medium 902 may encompass a recordablemedium 908, such as, but not limited to, memory, read/write (R/W) CDs,R/W DVDs, etc. In some implementations, signal bearing medium 902 mayencompass a communications medium 910, such as, but not limited to, adigital and/or an analog communication medium (e.g., a fiber opticcable, a waveguide, a wired communications link, a wirelesscommunication link, etc.). Thus, for example, program product 900 may beconveyed to one or more modules of user device 120 by an RF signalbearing medium 902, where the signal bearing medium 902 is conveyed by awireless communications medium 910 (e.g., a wireless communicationsmedium conforming with the IEEE 802.11 standard).

FIG. 10 is a block diagram illustrating an example computing device thatmay be utilized to provide a remote trash-can function, arranged inaccordance with at least some embodiments described herein.

In these examples, elements of computing device 1000 may be arranged orconfigured for an electronic device. In a very basic configuration 1002,computing device 1000 typically includes one or more processors 1004 anda system memory 1006. A memory bus 1008 may be used for communicatingbetween processor 1004 and system memory 1006.

Depending on the desired configuration, processor 1004 may be of anytype including but not limited to a microprocessor (μP), amicrocontroller C), a digital signal processor (DSP), or any combinationthereof. Processor 1004 may include one more levels of caching, such asa level one cache 1010 and a level two cache 1012, a processor core1014, and registers 1016. An example processor core 1014 may include anarithmetic logic unit (ALU), a floating point unit (FPU), a digitalsignal processing core (DSP Core), or any combination thereof. Anexample memory controller 1018 may also be used with processor 1004, orin some implementations memory controller 1018 may be an internal partof processor 1004.

Depending on the desired configuration, system memory 1006 may be of anytype including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. System memory 1006 may include an operating system 1020, one ormore applications 1022, and program data 1024. Application 1022 mayinclude instructions 1026 that may be arranged to perform the functionsas described herein including the actions described with respect to theuser device 120 architecture as shown in FIG. 4 or including the actionsdescribed with respect to the flow charts shown in FIGS. 6-7. In someexamples, application 1022 may be arranged to operate with program data1024 on an operating system 1020 such that implementations forinstructions for an electronic device as described herein.

Computing device 1000 may have additional features or functionality, andadditional interfaces to facilitate communications between basicconfiguration 1002 and any required devices and interfaces. For example,a bus/interface controller 1030 may be used to facilitate communicationsbetween basic configuration 1002 and one or more data storage devices1032 via a storage interface bus 1034. Data storage devices 1032 may beremovable storage devices 1036, non-removable storage devices 1038, or acombination thereof. Examples of removable storage and non-removablestorage devices include magnetic disk devices such as flexible diskdrives and hard-disk drives (HDD), optical disk drives such as compactdisk (CD) drives or digital versatile disk (DVD) drives, solid statedrives (SSD), and tape drives to name a few. Example computer storagemedia may include volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data.

System memory 1006, removable storage devices 1036 and non-removablestorage devices 1038 are examples of computer storage media. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich may be used to store the desired information and which may beaccessed by computing device 1000. Any such computer storage media maybe part of computing device 1000.

Computing device 1000 may also include an interface bus 1040 forfacilitating communication from various interface devices (e.g., outputdevices 1042, peripheral interfaces 1044, and communication devices1046) to basic configuration 1002 via bus/interface controller 1030.Example output devices 1042 include a graphics processing unit 1048 andan audio processing unit 1050, which may be configured to communicate tovarious external devices such as a display or speakers via one or moreA/V ports 1052. Example peripheral interfaces 1044 include a serialinterface controller 1054 or a parallel interface controller 1056, whichmay be configured to communicate with external devices such as inputdevices (e.g., keyboard, mouse, pen, voice input device, touch inputdevice, etc.) or other peripheral devices (e.g., printer, scanner, etc.)via one or more I/O ports 1058. An example communication device 1046includes a network controller 1060, which may be arranged to facilitatecommunications with one or more other computing devices 1062 over anetwork communication link via one or more communication ports 1064.

The network communication link may be one example of a communicationmedia. Communication media may typically be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A “modulateddata signal” may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.By way of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), microwave,infrared (IR) and other wireless media. The term computer readable mediaas used herein may include both storage media and communication media.

Computing device 1000 may be implemented as a portion of a small-formfactor portable (or mobile) electronic device such as a cell phone, apersonal data assistant (PDA), a personal media player device, awireless web-watch device, a personal headset device, an applicationspecific device, or a hybrid device that include any of the abovefunctions. Computing device 1000 may also be implemented as a personalcomputer including both laptop computer and non-laptop computerconfigurations.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as will be apparentto those skilled in the art. Functionally equivalent methods andapparatuses within the scope of the disclosure, in addition to thoseenumerated herein, will be apparent to those skilled in the art from theforegoing descriptions. Such modifications and variations are intendedto fall within the scope of the appended claims. The present disclosureis to be limited only by the terms of the appended claims, along withthe full scope of equivalents to which such claims are entitled. It isto be understood that this disclosure is not limited to particularmethods, reagents, compounds, compositions or biological systems, whichcan, of course, vary. It is also to be understood that the terminologyused herein is for the purpose of describing particular embodimentsonly, and is not intended to be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations). Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention (e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

In addition, where features or aspects of the disclosure are describedin terms of Markush groups, those skilled in the art will recognize thatthe disclosure is also thereby described in terms of any individualmember or subgroup of members of the Markush group.

As will be understood by one skilled in the art, for any and allpurposes, such as in terms of providing a written description, allranges disclosed herein also encompass any and all possible subrangesand combinations of subranges thereof. Any listed range can be easilyrecognized as sufficiently describing and enabling the same range beingbroken down into at least equal halves, thirds, quarters, fifths,tenths, etc. As a non-limiting example, each range discussed herein canbe readily broken down into a lower third, middle third and upper third,etc. As will also be understood by one skilled in the art all languagesuch as “up to,” “at least,” and the like include the number recited andrefer to ranges which can be subsequently broken down into subranges asdiscussed above. Finally, as will be understood by one skilled in theart, a range includes each individual member. Thus, for example, a grouphaving 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, agroup having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells,and so forth.

From the foregoing, it will be appreciated that various embodiments ofthe present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various embodiments disclosed herein are not intendedto be limiting, with the true scope and spirit being indicated by thefollowing claims.

1. A method performed under control of a user device, comprising:displaying a remote trash-can icon on a display of the user device;receiving a first user input that includes moving an icon representing alocally stored file to be discarded onto the remote trash-can icon;displaying on the display a request for a reason for discarding thelocally stored file; and moving the discarded file to a server.
 2. Themethod of claim 1, further comprising: receiving a second user inputthat is a response to the request; and transmitting the second userinput to the server.
 3. The method of claim 1, wherein the requestincludes an interactive menu that includes representations of variousreasons for discarding the locally stored file.
 4. The method of claim1, wherein the request is based at least in part on a type of thediscarded file.
 5. The method of claim 1, further comprising:transmitting to the server at least one of information about thediscarded file, information about the first user input, and informationabout the user device.
 6. The method of claim 5, wherein the informationabout the file includes at least one of a name, contents, a date ofcreation, a location of creation, and a date of last update.
 7. Themethod of claim 5, wherein the information about the first user inputincludes at least one of a time and a location of the first user input.8-13. (canceled)
 14. A method performed under control of a server,comprising: receiving from a user device a file discarded on the userdevice; receiving from the user device a reason for discarding the file;and storing the file and the reason locally.
 15. The method of claim 14,further comprising: receiving from the user device at least one ofinformation about the file, information about the discarding of thefile, and information about the user device.
 16. The method of claim 15,further comprising: examining the reason for discarding the file and theat least one of information about the file, information about thediscarding of the file, and information about the user device.
 17. Themethod of claim 15, wherein the information about the file includes atleast one of a name, contents, a date of creation, a location ofcreation, and a date of last update.
 18. The method of claim 15, whereinthe information about the discarding of the file includes at least oneof a time and a location of the discarding of the file by the user ofthe user device.
 19. A user device, comprising: a display configured todisplay a remote trash-can icon; a storage configured to store at leastone file; a user input handling unit configured to receive a first userinput that includes moving an icon representing at least one of thestored files to be discarded onto the remote trash-can icon; a controlunit configured to generate a request for a reason for discarding the atleast one file, the request being configured to be displayed on thedisplay; and a transmitting unit configured to move the at least onediscarded file to a server.
 20. The user device of claim 19, wherein theuser input handling unit is further configured to receive a second userinput that is a response to the request, and wherein the transmittingunit is further configured to transmit the second user input to theserver.
 21. The user device of claim 19, wherein the request includes aninteractive menu that includes representations of various reasons fordiscarding the at least one discarded file.
 22. The user device of claim19, wherein the request is based at least in part on a type of the atleast one discarded file.
 23. The user device of claim 19, wherein thetransmitting unit is further configured to transmit to the server atleast one of information about the at least one discarded file,information about the first user input, and information about the userdevice. 24-27. (canceled)
 28. A server, comprising: a receiving unitconfigured to receive from a user device a discarded file and a reasonfor discarding the discarded file; and a storage configured to store thediscarded file and the reason.
 29. The server of claim 28, wherein thereceiving unit is further configured to receive from the user device atleast one of information about the discarded file, information about thediscarding of the discarded file, and information about the user device.30. The server of claim 29, further comprising: an informationexamination unit configured to examine the reason for discarding thediscarded file and the information received from the user device. 31.(canceled)